-
WORD Research this...2 Chronicles 11
- 1 Da Rehabeam var kommet til Jerusalem, samlede han hele Judas og Benjamins Hus, 180 000 udsøgte Folk, øvede Krigere, til at føre Krig med Israel og vinde Kongedømmet tilbage til Rehabeam.
- 2 Men da kom HERRENS Ord til den Guds Mand Sjemaja saaledes:
- 3 »Sig til Judas Konge Rehabeam, Salomos Søn, og til hele Israel i Juda og Benjamin:
- 4 Saa siger HERREN: I maa ikke drage op og kæmpe med eders Brødre; vend hjem hver til sit, thi hvad her er sket, har jeg tilskikket!« Da adlød de HERRENS Ord og vendte tilbage og drog ikke mod Jeroboam.
- 5 Rehabeam boede saa i Jerusalem, og han befæstede flere Byer i Juda.
- 6 Saaledes befæstede han Betlehem, Etam, Tekoa,
- 7 Bet-Zur, Soko, Adullam,
- 8 Gat, Maresja, Zif,
- 9 Adorajim, Lakisj, Azeka,
- 10 Zor'a, Ajjalon og Hebron, alle i Juda og Benjamin;
- 11 og han gjorde Fæstningerne stærke, indsatte Befalingsmænd i dem og forsynede dem med Forraad af Levnedsmidler, Olie og Vin
- 12 og hver enkelt By med Skjolde og Spyd og gjorde dem saaledes meget stærke. Ham tilhørte Juda og Benjamin.
- 13 Præsterne og Leviterne i hele Israel kom alle Vegne fra, hvor de boede, og stillede sig til hans Tjeneste;
- 14 thi Leviterne forlod deres Græsmarker og Ejendom og begav sig til Juda og Jerusalem, fordi Jeroboam og hans Sønner afsatte dem fra Stillingen som HERRENS Præster,
- 15 idet han indsatte sig Præster for Offerhøjene og Bukketroldene og Tyrekalvene, som han, havde ladet lave.
- 16 Og i Følge med Leviterne kom fra alle Israels Stammer de, hvis Hjerte var vendt til at søge HERREN, Israels Gud, til Jerusalem for at ofre til HERREN, deres Fædres Gud;
- 17 og de styrkede Juda Rige og hævdede Rehabeams, Salomos Søns, Magt i et Tidsrum af tre Aar. Thi i tre Aar fulgte han Davids og Salomos Veje.
- 18 Rehabeam ægtede Mahalat; en Datter af Davids Søn Jerimot og Abihajil, en Datter af Eliab, Isajs Søn.
- 19 Hun fødte ham Sønnerne Je'usj, Sjemarja og Zaham.
- 20 Senere ægtede han Absaloms Datter Ma'aka, som fødte ham Abija, Attaj, Ziza og Sjelomit.
- 21 Rehabeam elskede Absaloms Datter Ma'aka højere end sine andre Hustruer og Medhustruer; han havde nemlig atten Hustruer og tresindstyve Medhustruer og avlede otte og tyve Sønner og tresindstyve Døtre.
- 22 Og Rehabeam satte Ma'akas Søn Abija til Overhoved, til Fyrste blandt hans Brødre; thi han havde i Sinde at gøre, ham til Konge;
- 23 og han fordelte klogelig alle sine Sønner rundt i alle Judas og Benjamins Landsdele og i alle de befæstede Byer og gav dem rigeligt Underhold og skaffede dem Hustruer.
-
-
King James Version (kjv)
- Afrikaans
- Arabic
- Armenian
- Basque
- Breton
- Chamorro
- Cherokee
- Chinese
- Coptic
- Croatian
- Czech
- Danish
- Dutch
-
English
American King James Version (akjv) American Standard Version (asv) Basic English Bible (basicenglish) Douay Rheims (douayrheims) John Wycliffe Bible (c.1395) (wycliffe) King James Version (kjv) King James Version (1769) with Strongs Numbers and Morphology and CatchWords, including Apocrypha (without glosses) (kjva) Webster's Bible (wb) Weymouth NT (weymouth) William Tyndale Bible (1525/1530) (tyndale) World English Bible (web) Young's Literal Translation (ylt)
- Esperanto
- Estonian
- Finnish
- French
- German
- Gothic
- Greek
- Greek Modern
- Hebrew
- Hungarian
- Italian
- Japanese
- Korean
- Latin
- Latvian
- Lithuanian
- Malayalam
- Manx Gaelic
- Maori
- Myanmar Burmse
- Norwegian bokmal
- Portuguese
- Potawatomi
- Romanian
- Russian
- Scottish Gaelic
- Slavonic Elizabeth
- Spanish
- Swahili
- Swedish
- Syriac
- Tagalog
- Thai
- Turkish
- Ukrainian
- Uma
- Vietnamese
-
-
Active Persistent Session:
To use a different persistent session key, simply add it above, and click the button below.
How This All Works
Your persistent session key, together with your favourite verse, authenticates you. It links to all your notes and tags in the Bible. You can share it with loved ones so they can see your notes and tags.
However, to modify your notes and tags, you need both the persistent session key and your favourite verse.
Please Keep Your Favourite Verse Private
Your persistent session key and favourite verse provide you exclusive access to edit your notes and tags. Think of your persistent session key as a username and your favourite verse as a password. Therefore, ensure your favourite verse is kept private.
The persistent session key allows viewing, while editing is only possible when the correct favourite verse is provided.
-
Loading...
-
-
Danish (danish - 1.0.2)
2017-05-22Danish (da)
Danish translation of the Old Testament authorized in 1931 by the Danish King, with the New Testment being the authorized Danish version from 1907.
The NT is based on an entirely new OCR-scanning of an edition with Latin typographic (not Fraktur). The NT has subsequently been thoroughly proof-read and hand-corrected, and footnotes
as well as tables of contents for each chapter have been added.
The OT is based on an OCR-scan from the late 1980s, scanned from a typographically deficient
edition from 1933. OCR-scanning done and proof-read by a Danish pioneering couple with a heart
for media-missions. It was placed on the Internet by Søren Horn in the early 1990s, from
where it was picked up by Projekt Runeberg at Linköping University. Ulrik Sandborg-Petersen picked
up the text in the mid-2000's, and has since then hand-corrected literally thousands of OCR-mistakes
and paragraphing issues.
Both the OT and the NT retain the original orthography.
Errors and corrections should be sent to Ulrik Sandborg-Petersen via:
https://github.com/emg/- Encoding: UTF-8
- Direction: LTR
- LCSH: Bible.Danish
- Distribution Abbreviation: danish
License
Public Domain
Source (OSIS)
https://github.com/emg/
- history_1.0
- (2017-05-20) Initial Release
- history_1.0.1
- (2017-5-21) added obsoletion notice to conf file for older module with same text from different source
- history_1.0.2
- (2022-08-09) Conf file corrections
- history_1..01
- (2017-05-22) Conf file corrections
Basic Hash Usage Explained
At getBible, we've established a robust system to keep our API synchronized with the Crosswire project's modules. Let me explain how this integration works in simple terms.
We source our Bible text directly from the Crosswire modules. To monitor any updates, we generate "hash values" for each chapter, book, and translation. These hash values serve as unique identifiers that change only when the underlying content changes, thereby ensuring a tight integration between getBible and the Crosswire modules.
Every month, an automated process runs for approximately three hours. During this window, we fetch the latest Bible text from the Crosswire modules. Subsequently, we compare the new hash values and the text with the previous ones. Any detected changes trigger updates to both our official getBible hash repository and the Bible API for all affected translations. This system has been operating seamlessly for several years.
Once the updates are complete, any application utilizing our Bible API should monitor the hash values at the chapter, book, or translation level. Spotting a change in these values indicates that they should update their respective systems.
Hash values can change due to various reasons, including textual corrections like adding omitted verses, rectifying spelling errors, or addressing any discrepancies flagged by the publishers maintaining the modules at Crosswire.
The Crosswire initiative, also known as the SWORD Project, is the "source of truth" for getBible. Any modifications in the Crosswire modules get reflected in our API within days, ensuring our users access the most precise and current Bible text. We pledge to uphold this standard as long as getBible exists and our build scripts remain operational.
We're united in our mission to preserve the integrity and authenticity of the Bible text. If you have questions or require additional information, please use our support system. We're here to assist and will respond promptly.
Thank you for your understanding and for being an integral part of the getBible community.
Favourite Verse
You should select one of your favourite verses.
This verse in combination with your session key will be used to authenticate you in the future.
This is currently the active session key.
Should you have another session key from a previous session.
You can add it here to load your previous session.